home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19971216-19980424
/
000274_news@newsmaster….columbia.edu _Sat Feb 28 15:56:40 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-04-22
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id PAA16891
for <kermit.misc@watsun.cc.columbia.edu>; Sat, 28 Feb 1998 15:56:39 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id PAA05381
for kermit.misc@watsun; Sat, 28 Feb 1998 15:56:39 -0500 (EST)
Path: news.columbia.edu!sol.ctr.columbia.edu!gondor!newshub1.wanet.net!uunet!in3.uu.net!ais.net!news-peer.sprintlink.net!news-peer-east.sprintlink.net!news.sprintlink.net!Sprint!rill.news.pipex.net!pipex!bore.news.pipex.net!pipex!join.news.pipex.net!pipex!krypton.inbe.net!INbe.net!be007054
From: michel.dalle@village.uunet.be (Michel Dalle)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Catching errors while executing 'run console-app' commands in K95 ?
Date: Sat, 28 Feb 1998 13:29:52 GMT
Organization: UUNET Benelux (post does not reflect views of UUNET Benelux)
Lines: 38
Message-ID: <6d8vrv$br1$1@xenon.inbe.net>
References: <6d6jic$q5a$1@horus.mch.sni.de> <6d6oq6$7bt$1@apakabar.cc.columbia.edu>
NNTP-Posting-Host: pool03-194-7-13-116.uunet.be
X-Newsreader: News Xpress 2.01
Xref: news.columbia.edu comp.protocols.kermit.misc:8466
In article <6d6oq6$7bt$1@apakabar.cc.columbia.edu>, fdc@watsun.cc.columbia.edu (Frank da Cruz) wrote:
>In article <6d6jic$q5a$1@horus.mch.sni.de>,
>Michel Dalle <Michel.Dalle@sni.be> wrote:
>: In a Kermit script, I want to launch a "console application" (something that
>: runs in the DOS box of Windows 95 and NT). The console application returns a
>: status of 0 if everything is OK, and it sends some messages to STDOUT. If
>: the console application failes, it returns a status of 1, 2, 3, ... and
>: prints a corresponding message to STDERR (this can be modified if needed).
>...
>: 2) know whether the console application executed correctly or not.
>:
>This depends on the program's exit status code. However, K95 has a bug in
>which the return code of a program or command that you start from K95 is not
>captured. This bug is fixed in 1.1.16, to be announced shortly.
>...
>: From what I've seen in tests, \v(status) and \v(exitstatus) always return 0,
>: and \v(pexitstat) always returns 1, independently of the success or failure
>: of the console application (at least on Windows 95... ).
>:
>Right, that's the bug described above. We'll have a fix for you soon.
>
Sorry to be pushy, but any idea when 1.1.16 is going to be available exactly ?
On the Kermit Website, it mentions March 1998, but is this tomorrow or on the
31st of March ? The reason I ask is because I'm right in the middle of coding
a script for a financial institution, and tests are planned for the end of the
week.
I need to do some file modifications during the script, and I wanted to do
that in a separate program because Kermit scripts were not the most
appropriate tool (for that). But if I can't reliably catch errors this way,
I'll have to do the file modifications in Kermit itself (ouch), or create an
error file if things go wrong in the console app (similar to what's do like in
host.ksc when executing DOS commands).
Any ideas ?
And do all these error catching problems also occur on Windows NT ?
Michel.